Media-object binding for dynamic generation and displaying of play data associated with media

ABSTRACT

A system and method for dynamic generation and display of play data for a media is provided. One or more sets of object data may be associated with the media. One or more media-object bindings between the one or more sets of object data and the media may be formed and stored in one or more databases. The one or more sets of object data may include data about an aspect displayed during at least the portion of the media. One or more object-object associations between the one or more sets of object data and one or more named objects of a metadata reference container, which may maintain a common schema based on commonly experienced characteristics, may be formed and stored the one or more databases. Play data may be dynamically generated based on the one or more media-object bindings and/or one or more object-object associations.

BACKGROUND 1. Technical Field

The present technology pertains to media-object binding. More specifically, the present technology may provide for dynamic generation and display of play data associated with media, including live-streaming media.

2. Background

Gaming media is an increasingly popular and growing information source for game players. Such gaming media (e.g., from a game publisher or game-related content created by peer players) may incentivize further gameplay, promote new features of a game or a new game, or provide gameplay help. Presently available gaming media be shared with one or more viewers by having a player broadcast their gameplay in a live-streaming or recorded media. Viewers may have a particular interest in learning about the various objects in a game or broadcast being shown on the screen. Such objects may include player information, game location information, game character information, game weapon information, and other objects that would be of interest to a viewer watching a media, such as game media.

There is, therefore, a need in the art for systems and methods for dynamically generating play data to be displayed in association with media, such as a live-streaming game.

SUMMARY

Aspects of the present disclosure include systems and methods for dynamic generation and display of play data for a media. The one or more sets of object data associated with the media may be stored in memory. The media (e.g., user-generated content or publisher content) may depict one or more objects. The media may be a live-streaming media. The media may have a length of time. The one or more sets of object data may include information or play data about the one or more objects displayed in the media, which may be associated with other objects associated with a common activity displayed in the media. The one or more sets of object data may include at least one timestamp corresponding to time within the media. The one or more sets of object data may include data about an object type, object information, such as changes available for activities, whether activities started or ended, activities most recently started, location change of a user, actor (e.g., an entity with behavior in the game, user-controlled or game-controlled) information, mechanic (e.g., objects and abilities that impact gameplay) information, and/or any other gameplay information.

The one or more sets of object data may be associated with the media. One or more media-object bindings between the one or more sets of object data and the media may be formed and stored in memory, such as one or more databases. Each set of object data may include data about one or more objects displayed during at least a portion of the media. One or more media-object bindings between the one or more sets of object data and the media may be formed and stored in one or more databases. One or more object-object associations between the one or more sets of object data and one or more named objects of a metadata reference container may be formed and stored in the one or more databases.

The metadata reference container may maintain a common schema based on commonly experienced characteristics of the media, such as a live-streaming gameplay media. The metadata reference container may be edited in order to include new and different commonly experienced characteristics or edit and modify preexisting metadata references. The common schema may be updated for new associations to form with the one or more sets of object data The one or more object-object associations and/or the one or more object-media bindings may be used to dynamically generate play data to be displayed along with the media. The play data may provide more information about the one or more objects displayed during at least the portion of the media that the one or more sets of object data is associated to. The play data may then be sent to an associated device to be displayed during in at least the portion of the media based on the one or more media-object bindings. The associated device may have sent the data about the one or more objects displayed (e.g., the player's device) or may be another device that is streaming the media (e.g., a device of a viewer/non-player of the media).

Various aspects of the present disclosure may include methods of dynamic generation and display of play data for a media. Such methods may include as associating one or more sets of object data with the media to form one or more media-object bindings, wherein the one or more sets of object data comprises data about one or more objects displayed during in at least a portion of the media. The one or more media-object bindings may be stored in one or more databases. Such methods may include associating the one or more sets of object data with one or more named objects of a metadata reference container that maintains the common schema based on commonly experienced characteristics, the associating may form one or more object-object associations. Such methods may include dynamically generating the play data based on the one or more object-object associations that may be displayed concurrently with the media. Such methods may include sending the play data to be displayed during in at least the portion of the media based on the one or more media-object bindings.

Additional aspects of the present disclosure may include systems for dynamic generation and display of the play data for the media. Such systems may include memory that stores streaming media, sets of object data, media-object bindings between stored object data and the media, and object-object associations between object data and named objects from the metadata reference container. Such system may include one or more processors that executes instructions stored in memory. Execution of the instructions by the one or more processors may associate one or more sets of object data with the media to form one or more media-object bindings, wherein the one or more sets of object data comprises data about one or more objects displayed during in at least a portion of the media and the one or more media-object bindings are stored in one or more databases. Execution of the instructions by the one or more processors may associate the one or more sets of object data with one or more named objects of the metadata reference container that maintains a common schema based on commonly experienced characteristics, the associating forming the one or more object-object associations. Execution of the instructions by the one or more processors may form and store the one or more object-object associations between the one or more sets of object data and other stored data in the one or more databases. The one or more object-object associations may dynamically generate the play data based on the one or more object-object associations to be displayed along with the media. Execution of the instructions by the one or more processors may send the play data to be displayed during in at least the portion of the media based on the one or more media-object bindings.

Further aspects of the present disclosure include non-transitory computer-readable medium or storage media having embodied thereon a program executable by a processor to provide a method for dynamic generation and display of play data for the media.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example network environment in which a system for searching within streaming media may be implemented, according to an aspect of the present disclosure;

FIG. 2A illustrates a detailed example network in which a system for dynamic generation and display of the play data for the media may be implemented, according to an aspect of the present disclosure;

FIG. 2B illustrates an example table of various objects and associated events, according to an aspect of the present disclosure;

FIG. 2C illustrates an example screenshot of the media displayed with the play data in accordance with an aspect of the present disclosure;

FIG. 3 illustrates a flowchart of an example method for dynamic generation and display of play data for the media, according to an aspect of the present disclosure; and

FIG. 4 illustrates an example electronic entertainment system that may be used in dynamic generation and display of the play data for the media, according to an aspect of the present disclosure.

DETAILED DESCRIPTION

The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the technology can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the technology. However, it will be clear and apparent that the technology is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject technology.

Aspects of the present disclosure include systems and methods for dynamic generation and display of play data for a media (e.g., displaying play data along with an associated gameplay stream). The media and one or more sets of object data associated with the media may be stored in memory. The one or more sets of object data may be associated with the media. One or more media-object bindings between the one or more sets of object data and the portion of the media may be stored in memory. Each set of object data may include data about one or more objects displayed during at least the portion of the media. The media-object bindings between the one or more sets of object data and the media may be formed in one or more databases. One or more object-object associations between the one or more sets of object data and one or more named objects of a metadata reference container that maintains a common schema based on commonly experienced characteristics. The commonly experienced characteristics may be for a plurality of different streaming media for different games provided by different media streaming servers. Play data may then be dynamically generated, based on the one or more object-object associations, to be displayed along with the media. The play data may then be sent to be displayed during in at least the portion of the media based on the one or more media-object bindings.

FIG. 1 illustrates an example network environment 100 in which a system for dynamically generating and displaying of the play data for the media. The network environment 100 may include one or more media streaming servers 110 that provide streaming content (e.g., interactive video, podcasts, etc.), one or more platform servers 120, one or more user devices 130, and one or more databases 140.

Media streaming servers 110 may maintain, stream, and host interactive media available to stream on a user device 130 over a communication network. Such media streaming servers 110 may be implemented in the cloud (e.g., one or more cloud servers). Each media may include one or more sets of object data that may be available for participation with (e.g., viewing or interacting with an activity) by a user. Data about the object shown in the media may be stored by the media streaming servers 110, platform servers 120 and/or the user device 130, in an object file 216, as will be discussed in detail with respect to FIGS. 2A and 3.

The platform servers 120 may be responsible for communicating with the different media streaming servers 110, databases 140, and user devices 130. Such platform servers 120 may be implemented on one or more cloud servers. The streaming servers 110 may communicate with multiple platform servers 120, though the media streaming servers 110 may be implemented on one or more platform servers 120. The platform servers 120 may also carry out instructions, for example, receiving a user request from a user to stream media (i.e., games, activities, video, podcasts, User Generated Content, publisher content, etc.). The platform servers 120 may further carry out instructions, for example, for streaming the media content titles. Such media may have at least one object set associated with the media. Each set of object data may have data about an object (e.g., activity information, zone information, actor information, mechanic information, game media information, etc.) displayed during at least a portion of the media content.

The media and the associated one or more sets of object data may be provided through an application programming interface (API) 160, which allows various types of media streaming servers 110 to communicate with different platform servers 120 and different user devices 130. API 160 may be specific to the particular computer programming language, operating system, protocols, etc., of the media streaming servers 110 providing the media content titles, the platform servers 120 providing the media and the associated one or more sets of object data, and user devices 130 receiving the same. In a network environment 100 that includes multiple different types of media streaming servers 110 (or platform servers 120 or user devices 130), there may likewise be a corresponding number of APIs 160.

The user device 130 may include a plurality of different types of computing devices. For example, the user device 130 may include any number of different gaming consoles, mobile devices, laptops, and desktops. In another example, the user device 130 may be implemented in the cloud (e.g., one or more cloud servers). Such user device 130 may also be configured to access data from other storage media, such as, but not limited to memory cards or disk drives as may be appropriate in the case of downloaded services. Such devices 130 may include standard hardware computing components such as, but not limited to network and media interfaces, non-transitory computer-readable storage (memory), and processors for executing instructions that may be stored in memory. These user devices 130 may also run using a variety of different operating systems (e.g., iOS, Android), applications or computing languages (e.g., C++, JavaScript). An example user device 130 is described in detail herein with respect to FIG. 4.

The databases 140 may be stored on the platform server 120, the media streaming servers 110, any of the servers 218 (shown in FIG. 2A), on the same server, on different servers, on a single server, across different servers, or on any of the user devices 130. Such databases 140 may store media and an associated set of object data. Such media may depict one or more activities that a user can participate in and/or UGC (e.g., screen shots, videos, commentary, mashups, etc.) created by peers, publishers of the media content titles and/or third party publishers. Such UGC may include metadata by which to search for such UGC. Such UGC may also include information about the media and/or peer. Such peer information may be derived from data gathered during peer interaction with an object of an interactive content title (e.g., a video game, interactive book, etc.) and may be “bound” to and stored with the UGC. Such binding enhances UGC as the UGC may deep link (e.g., directly launch) to an object, may provide for information about an object and/or a peer of the UGC, and/or may allow a user to interact with the UGC. One or more user profiles may also be stored in the databases 140. Each user profile may include information about the user (e.g., user progress in an activity and/or media content title, user id, user game characters, etc.) and may be associated to media.

In the example network environment 200 of FIG. 2A, an example console 228 (e.g., a user device 130) and example servers 218 (e.g., streaming server 220, activity feed server 224, UGC server 232, and object server 226) are shown. In one example, the console 228 may be implemented on the platform server 120, a cloud server, or on any of the servers 218. In an example, a content recorder 202 may be implemented on the platform server 120, a cloud server, or on any of the servers 218. Such content recorder 202 receives and records content (e.g., media) from an interactive content title 230 onto a content ring-buffer 208. Such ring-buffer 208 may store multiple content segments (e.g., v1, v2 and v3), start times for each segment (e.g., V1_START_TS, V2_START_TS, V3_START_TS), and end times for each segment (e.g., V1_END_TS, V2_END_TS, V3_END_TS). Such segments may be stored as a media file 212 (e.g., MP4, WebM, etc.) by the console 228. Such media file 212 (e.g., a portion of the live-streaming media) may be uploaded to the streaming server 220 for storage and subsequent streaming or use, though the media file 212 may be stored on any server, a cloud server, any console 228, or any user device 130. The media file 212 may be uploaded periodically and/or in real-time or close to real-time. Such start times and end times for each segment may be stored as a content time stamp file 214 by the console 228. Such content time stamp file 214 may also include a streaming ID, which matches a streaming ID of the media file 212, thereby associating the content time stamp file 214 to the media file 212. Such content time stamp file 214 may be uploaded and stored to the activity feed server 224 and/or the UGC server 232, though the content time stamp file 214 may be stored on any server, a cloud server, any console 228, or any user device 130.

Concurrent to the content recorder 202 receiving and recording content from the interactive content title 230, an object library 204 receives data from the interactive content title 230, and an object recorder 206 tracks the data to determine when an object beings and ends. The object library 204 and the object recorder 206 may be implemented on the platform server 120, a cloud server, or on any of the servers 218. When the object recorder 206 detects an object beginning, the object recorder 206 receives object data (e.g., if the object were an activity, user interaction with the activity ID, activity start times, activity end times, activity results, activity types, etc.) from the object library 204 and records the activity data onto an object ring-buffer 210 (e.g., ActivityID1, START_TS; ActivityID2, START_TS; ActivityID3, START_TS). Such activity data recorded onto the object ring-buffer 210 may be stored in the object file 216. Such object file 216 may also include activity start times, activity end times, an activity ID, activity results, activity types (e.g., competitive match, quest, task, etc.), user or peer data related to the activity. For example, an object file 216 may store data regarding an item used during the activity. Such object file 216 may be stored on the object server 226, though the object file 216 may be stored on any server, a cloud server, any console 228, or any user device 130.

Such object data (e.g., the object file 216) may be associated with the content data (e.g., the media file 212 and/or the content time stamp file 214). In one example, the UGC server 232 stores and associates the content time stamp file 214 with the object file 216 based on a match between the streaming ID of the content time stamp file 214 and a corresponding activity ID of the object file 216. In another example, the object server 226 may store the object file 216 and may receive a query from the UGC server 232 for an object file 216. Such query may be executed by searching for an activity ID of an object file 216 that matches a streaming ID of a content time stamp file 214 transmitted with the query. In yet another example, a query of stored content time stamp files 214 may be executed by matching a start time and end time of a content time stamp file 214 with a start time and end time of a corresponding object file 216 transmitted with the query. Such object file 216 may also be associated with the matched content time stamp file 214 by the UGC server 232, though the association may be performed by any server, a cloud server, any console 228, or any user device 130. In another example, an object file 216 and a content time stamp file 214 may be associated by the console 228 during creation of each file 216, 214.

As shown in the exemplary table 250 of FIG. 2B, such object data (e.g., the object file 216) may be associated with event information regarding activity availability change and may be related to other objects with associated event information. For example, such object data may be zone data files 252, actor data files 254, mechanics data files 256, game media data files 258, and other gameplay-related data files.

Such object data (e.g., the object file 216) may be categorized as in in progress, open-ended, or competitive. Such activity data files 216 may include optional properties, such as a longer description of the activity, an image associated with the activity, if the activity is available to players before launching the game, whether completion of the activity is required to complete the game, whether the activity can be played repeatedly in the game, and whether there are nested tasks or associated child activities. Such activity data files 216 may include an activity availability change event for, which may indicate a list or array of currently available activities for the player. For example, this may be used to decide what activities to display in a game plan.

Such zone data files 252 may indicate an area of an associated game world with a single coordinate system wherein the zone may have a 2-D map associated with it, and may be used to display locations on the zone. If zone data files 252 are applicable, each zone may include a zone ID and a short localizable name of the Zone. Such zone data files 252 may be associated with a view projection matrix (4×4) to convert from 3-D world coordinates to a 2-D map position. Such zone data files 252 may be associated with a location change event that indicates an update to a current in-game location of the player. Such location change event may be posted regularly, or whenever the player's in-game location changes significantly. The platform server 120 may store a latest value in ‘state.’ Such zone data files 252 may include an x, y, z position of the player's character in the zone as well as an a, b, c vector indicating the player's characters orientation or direction. Such zone data files 252 may be associate with an activity start event and/or an activity end event and for the activity end event, an outcome of completed, failed, or abandoned may be associated to the activity (e.g., activity ID).

Such actor data files 254 may be associated with an entity with behaviors in the game, and can be player-controller or game-controlled, and can change dynamically during gameplay. Such actor data files 254 may include an actor ID for the actor, a localizable name for the actor, an image of the actor, and/or a short description of the actor. Such actor data files 254 may be associated with an actor select event that indicates that the player's selected actor(s) have changed. The selected actor(s) may represent the actors the player is controlling in the game and may be displayed on the player's profile and other spaces via the platform server 120. There may be more than one actor selected at time and each game may replace its list of actors upon loading save data.

Such mechanics data files 256 may be associated with an item, skill, or effect that can be used by the player or the game to impact gameplay (e.g., bow, arrow, stealth attack, fire damage) and may exclude items that do no impact gameplay (e.g., collectibles). Such mechanics data files 256 may include a mechanic ID of the mechanic, a short name of the mechanic, an image of the mechanic, and/or a short description of the mechanic. Such mechanics data files 256 may be associated with a mechanic availability change event that indicates that the mechanics available to the player have changed. Available may mean that the mechanic is available in the game world for the player to use, but may require the player to go through some steps to acquire it into inventory (e.g., buy from a shop, pick up from the world) before using it. Each game may replace its list of mechanics upon loading save data.

Such mechanics data files 256 may be associated with a mechanic inventory change event that indicates that the player's inventory has changed. Inventory may refer to mechanics that are immediately usable to the player without having to take additional steps in the game before using it. Inventory information is used to estimate a player's readiness for various activities, which may be forwarded to the platform server 120. Games may replace its list of mechanic inventory upon loading save data. Mechanics on cool down may be considered part of the inventory. Mechanic counts (e.g., ammunition, healing points) with any non-zero value may be treated as “in inventory.” Inventory mechanics may be considered a subset of available mechanics.

Such mechanics data files 256 may be associated with a mechanic use event that indicates that a mechanic has been used by or against the player and may be used to be displayed as mechanic usage in a UGC context. Such mechanics data files 256 may include a list or array of mechanics that were used (e.g, fire arrow, fire damage) or whether an initiator is the player, such that whether the mechanics were used by or against the player. Such mechanics data files 256 may include an initiator actor ID, a current zone ID of the initiator actor, and/or a current x, y, z position of the initiator actor. Such mechanics data files 256 may be associated with a mechanic impact event that indicates that a mechanic had impact on gameplay (e.g., an arrow hit an enemy) and may be used to display mechanic image in a UGC context. Mechanic use and mechanic image events may be not linked. Such mechanics data files 256 may include the initiator action ID, the current zone ID of the initiator actor, the current x, y, z position of the initiator actor, a target actor ID, a current zone ID of the target actor, a current x, y, z of the target actor, and a mitigation mechanic that may mitigate the initiator mechanic.

Such game media data files 258 may be include a game media ID of the game media, a localizable name for the game media, a media format (e.g., image, audio, video, text, etc.), a category or type of media (cut-scene, audiolog, poster, developer commentary, etc.), a URL or a server-provisioned media file, and/or whether the game media is associated with a particular activity. Such game media data files 258 may be associated with a game media start event that indicates that a particular piece of game media has started in the game right now and a game media end event that indicates that the particular piece of game media has ended.

Object data (e.g., activity data, zone data, actor data, mechanics data, etc.) may be associated with one or more named objects of a metadata reference container that may maintain a common schema based on commonly experienced characteristics to form object-object associations. The metadata reference container may be edited in order to include new and different commonly experienced characteristics or edit and modify preexisting metadata references, such as new or different types of object data and/or the metadata associated with the object data. The common schema may be updated for new associations to form with the one or more sets of object data. The object data may also be associated with the media files (e.g., media file 212) and for media-object bindings. Media-object bindings form telemetry between the objects shown in a media and the media. These object-object associations and media-object bindings, along with other associations made with respect to objects (e.g., activities, actors, actions, etc.) displayed in the media, may allow for dynamic generation of play data (see e.g., play data 276 in FIG. 2C below) to be displayed along with the media (see e.g., streaming media 275 in FIG. 2C below). The play data associated with object data may provide a viewer of the media more insight as to objects displayed in the media (e.g., gameplay stream) such that the viewer of the media may have more in-depth analysis while the media is concurrently being displayed. The media along with the play data may be displayed as a live stream wherein the play data is also dynamically generated and sent to be displayed live or may be broadcasted after and the play data is dynamically generated and sent to be displayed as it is broadcasted after.

FIG. 2C illustrates an example screenshot of the media 275 displayed with play data 276 in accordance with an aspect of the present disclosure. The play data 276 may include detailed information 278 regarding the object data, such as the character selected, mechanics selected or available. Additional information may be supplemented to the common schema by respective media streaming servers (e.g., interactive content source servers 110) in order to provide in-depth and game-specific play data 276. The common schema may define or organize object data for a plurality of games or other kinds of streaming media as a single merged asset. Example metadata may include game telemetry (e.g., zone data, activity data, actor data, mechanics data). Other detailed information 278 may include showing a map and/or other similar kinds of gameplay data. If available, there may be a purchase option 280 to purchase coordinates for finding the mechanics. The purchase option 280 may be for other kinds of information for other object data. The play data 276 may be presented to as game insights in a new data presentation layer for viewers streaming the media to have a more dynamic and comprehensive view.

FIG. 3 is a flowchart illustrating an example method 300 for dynamic generation and display of the play data for the media. The method 300 of FIG. 3 may be embodied as executable instructions in a non-transitory computer readable storage medium including but not limited to a CD, DVD, or non-volatile memory such as a hard drive. The instructions of the storage medium may be executed by one or more processors to cause various hardware components of a computing device hosting or otherwise accessing the storage medium to effectuate the method. The execution of the instructions may be implemented on the cloud servers (e.g., the steps identified in FIG. 3 are performed in the cloud). The steps identified in FIG. 3 (and the order thereof) are example and may include various alternatives, equivalents, or derivations thereof including but not limited to the order of execution of the same.

In step 310, at least one set of object data (e.g., at least one activity file 216) generated based on the one or more objects displayed in the media (e.g., a media file 212). In step 320, the at least one set of object data is associated with at least a portion of the media. The at least one set of object data may comprises data about the one or more objects displayed with the media. If the media is a live-streaming media, the at least one set of objects may comprise data about the one or more objects displayed during at least a portion of the live-streaming media. Such association or binding may be based on at least one timestamp of the set of object data associated with one or more timestamps (e.g., a content time stamp file 214) of the media. In addition to or alternatively, such association or binding may be based on an activity ID of the set of object data associated with a media ID of the media, wherein the set of object data may also include data about the one or more objects displayed during at least a portion of the media (e.g., activity results, activity types (e.g., competitive match, quest, task, etc.), user or peer data related to the activity). The set of object data may also include a direct link to the associated object. Such link allows a user to directly access an object. For example, a user may wish to participate in an activity associated with the object shown by the media. In the same example, the user can select an option to play the activity shown, and the activity may be automatically launched after selection by the user.

In step 330, based on the association, one or more media-object bindings are formed between the at least one set of object data and the at least a portion of the media. In step 340, the one or more media-object bindings are stored in the database 140 or the user devices 130 by the media streaming servers 110 or the platform servers 120. The media may be part of an interactive content title 230 or may be UGC (e.g., help video, screen shots, videos, commentary, mashups, etc.) generated by the user, peers, a publisher of the media content title, or a third party. One or more user profiles may also be stored in the database 140 or the user devices 130 by the media streaming servers 110 or the platform servers 120.

One or more object-object associations may be formed between the one or more sets of object data and one or more named objects of the metadata reference container, which may be stored as one of the one or more databases (e.g., the database 140) or may be a portable metadata reference container that is accessible via a connection. The portable metadata reference container may be continuously updated so that the common schema is comprehensive with respect to gameplay data for all of the media streaming servers 110. For example, if the media displays a “Defense Shield” mechanic, one or more sets of object data associated with the “Defense Shield” mechanic are associated with the media, more specifically with a timestamp during which the “Defense Shield” mechanic is shown or relevant, forming one or more media-object bindings.

In step 350, the one or more media-object bindings and/or object-object associations may be a basis for dynamically generating play data to be displayed along with the media. In following the example above, the one or more sets of object data associated with the “Defense Shield” mechanic may be associated with the one or more named objects of the metadata reference container, such as more detailed data pertaining to the “Defense Shield” mechanic, forming the one or more object-object associations.

In step 360, the play data may be sent to be displayed during in at least the portion of the media, based on the one or more media-object bindings. The dynamic generation of the play data may be an automatic generation such that the play data to be displayed with the media may only be shown when the one or more objects is shown on the media and removed from displayed once the one or more objects are no longer shown on the media and/or shortly thereafter. Therefore, the play data shown concurrently with the media is associated with the one or more objects shown in the media and/or shortly thereafter. Again, in following the example above, when the media is broadcasted, live or afterwards, while the “Defense Shield” mechanic is in play, a viewer of the media has the ability to view more details about the “Defense Shield” mechanic (e.g., similar to how a player may have access to similar data while playing the game and even more so). The play data may include more detailed information regarding one or more objects displayed in the media, an option to purchase regarding one or more objects displayed in the media, and/or an option to purchase related information or gameplay options.

FIG. 4 is an example user electronic entertainment system that may be used in launching interactive content and providing dynamic interfaces. The entertainment system 400 of FIG. 4 includes a main memory 405, a central processing unit (CPU) 410, vector unit 415, a graphics processing unit 420, an input/output (I/O) processor 425, an I/O processor memory 430, a peripheral interface 435, a memory card 440, a Universal Serial Bus (USB) interface 445, and a communication network interface 450. The entertainment system 400 further includes an operating system read-only memory (OS ROM) 455, a sound processing unit 460, an optical disc control unit 470, and a hard disc drive 465, which are connected via a bus 475 to the I/O processor 425.

Entertainment system 400 may be an electronic game console. Alternatively, the entertainment system 400 may be implemented as a general-purpose computer, a set-top box, a hand-held game device, a tablet computing device, a virtual reality device, an augmented reality device, or a mobile computing device or phone. Entertainment systems may contain more or less operating components depending on a particular form factor, purpose, or design.

The CPU 410, the vector unit 415, the graphics processing unit 420, and the I/O processor 425 of FIG. 4 communicate via a system bus 485. Further, the CPU 410 of FIG. 4 communicates with the main memory 405 via a dedicated bus 480, while the vector unit 415 and the graphics processing unit 420 may communicate through a dedicated bus 490. The CPU 410 of FIG. 4 executes programs stored in the OS ROM 455 and the main memory 405. The main memory 405 of FIG. 4 may contain pre-stored programs and programs transferred through the I/O Processor 425 from a CD-ROM, DVD-ROM, or other optical disc (not shown) using the optical disc control unit 470. I/O Processor 425 of FIG. 4 may also allow for the introduction of content transferred over a wireless or other communications network (e.g., 4G, LTE, 1G, and so forth). The I/O processor 425 of FIG. 4 primarily controls data exchanges between the various devices of the entertainment system 400 including the CPU 410, the vector unit 415, the graphics processing unit 420, and the peripheral interface 435.

The graphics processing unit 420 of FIG. 4 executes graphics instructions received from the CPU 410 and the vector unit 415 to produce images for display on a display device (not shown). For example, the vector unit 415 of FIG. 4 may transform objects from three-dimensional coordinates to two-dimensional coordinates, and send the two-dimensional coordinates to the graphics processing unit 420. Furthermore, the sound processing unit 460 executes instructions to produce sound signals that are outputted to an audio device such as speakers (not shown). Other devices may be connected to the entertainment system 400 via the USB interface 445, and the communication network interface 450 such as wireless transceivers, which may also be embedded in the system 400 or as a part of some other component such as a processor.

A user of the entertainment system 400 of FIG. 4 provides instructions via the peripheral interface 435 to the CPU 410, which allows for use of a variety of different available peripheral devices (e.g., controllers) known in the art. For example, the user may instruct the CPU 410 to store certain game information on the memory card 440 or other non-transitory computer-readable storage media or instruct a character in a game to perform some specified action.

The present disclosure pertain to an application that may be operable by a variety of end user devices. For example, an end user device may be a personal computer, a home entertainment system (e.g., Sony PlayStation2® or Sony PlayStation3® or Sony PlayStation4®), a portable gaming device (e.g., Sony PSP® or Sony Vita®), or a home entertainment system of a different albeit inferior manufacturer. The present methodologies described herein are fully intended to be operable on a variety of devices. Aspects of the present disclosure may also be implemented with cross-title neutrality and/or may be utilized across a variety of titles from various publishers.

Aspects of the present disclosure may be implemented in an application that may be operable using a variety of devices. Non-transitory computer-readable storage media refer to any medium or media that participate in providing instructions to a central processing unit (CPU) for execution. Such media can take many forms, including, but not limited to, non-volatile and volatile media such as optical or magnetic disks and dynamic memory, respectively. Common forms of non-transitory computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, RAM, PROM, EPROM, a FLASHEPROM, and any other memory chip or cartridge.

Various forms of transmission media may be involved in carrying one or more sequences of one or more instructions to a CPU for execution. A bus carries the data to system RAM, from which a CPU retrieves and executes the instructions. The instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU. Various forms of storage may likewise be implemented as well as other network interfaces and network topologies to implement the same.

In some aspects of the present disclosure, computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

The foregoing detailed description of the technology has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described aspects of the present disclosure were chosen in order to adequately explain the principles of the technology, its practical application, and to enable others skilled in the art to utilize the technology along with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claim. 

What is claimed is:
 1. A method of dynamic generation and display of play data for a media file, the method comprising: recording a plurality of media files generated based on one or more inputs from a client device, wherein a plurality of object files are recorded simultaneously; associating one or more sets of object data of the plurality of object files with at least a media file of the plurality of media files, wherein the one or more sets of object data comprises data about one or more objects displayed in the media file; forming, based on the associating, one or more media-object bindings between the one or more sets of object data and the at least the media file; storing the one or more media-object bindings in one or more databases; dynamically generating, based on the one or more sets of object data and the one or more media-object bindings, the play data associated with the media file; and displaying the play data in association the media file.
 2. The method of claim 1, wherein the associating the one or more sets of object data with the media file to form the one or more media-object bindings further including associating a timestamp at which an associated object is displayed during in at least the media file.
 3. The method of claim 2, further comprising: sending the play data to be played simultaneously with at least the media file based on the one or more media-object bindings.
 4. The method of claim 3, wherein the sending further includes sending the timestamp so that the play data is displayed while the associated object is displayed during in at least the media file.
 5. The method of claim 1, further comprising: associating the one or more sets of object data with one or more named objects of a metadata reference container that maintains a common schema based on commonly experienced characteristics, the associating forming one or more object-object associations, wherein the play data is dynamically generated based on at least the one or more object-object associations.
 6. The method of claim 5, wherein the metadata reference container maintains the common schema based on the commonly experienced characteristics for a plurality of different streaming media for different games provided by different media streaming servers.
 7. The method of claim 5, wherein for different games, additional information are supplemented to the common schema by respective media streaming servers in order to provide in-depth and game-specific play data.
 8. The method of claim 1, wherein the play data further includes more detailed information regarding the one or more objects displayed in the media file.
 9. The method of claim 1, wherein the play data further includes an option to purchase regarding the one or more objects displayed in the media file.
 10. The method of claim 1, wherein the play data further includes an option to purchase related information or gameplay options.
 11. The method of claim 1, wherein the media file along with the play data are displayed as a live stream.
 12. A system for dynamic generation and display of play data for a media file, the system comprising: one or more databases that store sets of object data, media-object bindings between the sets of object data and the media file, and object-object associations; and one or more processors that execute instructions stored in memory, wherein execution of the instructions by the one or more processors: records a plurality of media files generated based on one or more inputs from a client device, wherein a plurality of object files are recorded simultaneously; associates one or more sets of object data of the plurality of object files with at least a media file of the plurality of media files, wherein the one or more sets of object data comprises data about one or more objects displayed in the media file; forms, based on the associating, one or more media-object bindings between the one or more sets of object data and the at least the media file; stores the one or more media-object bindings in the one or more databases; dynamically generates, based on the one or more sets of object data and the one or more media-object bindings, the play data associated with the media file; and displays the play data in association the media file.
 13. The system of claim 12, wherein the associating the one or more sets of object data with the media file to form the one or more media-object bindings further including associating a timestamp at which an associated object is displayed during in the at least the media file.
 14. The system of claim 13, further comprising: sending the play data to be played simultaneously with the at least the media file based on the one or more media-object bindings.
 15. The system of claim 14, wherein the sending further includes sending the timestamp so that the play data is displayed while the one or more objects are displayed during in the at least the media file.
 16. The system of claim 12, further comprising: associating the one or more sets of object data with one or more named objects of a metadata reference container that maintains a common schema based on commonly experienced characteristics, the associating forming one or more object-object associations, wherein the play data is dynamically generated based on at least the one or more object-object associations.
 17. The system of claim 16, wherein the metadata reference container maintains the common schema based on the commonly experienced characteristics for a plurality of different streaming media for different games provided by different media streaming servers.
 18. The system of claim 16, wherein for different games, additional information are supplemented to the common schema by respective media streaming servers in order to provide in-depth and game-specific play data.
 19. The system of claim 12, wherein the play data further includes more detailed information regarding one or more objects displayed in the media file.
 20. The system of claim 12, wherein the play data further includes an option to purchase regarding one or more objects displayed in the media file.
 21. The system of claim 12, wherein the play data further includes an option to purchase related information or gameplay options.
 22. The system of claim 12, wherein the media file along with the play data are displayed as a live stream.
 23. A non-transitory computer-readable medium having embodied thereon a program executable by one or more processors to perform a method for dynamic generation and display of play data for a media file, the method comprising: recording a plurality of media files generated based on one or more inputs from a client device, wherein a plurality of object files are recorded simultaneously; associating one or more sets of object data of the plurality of object files with at least a media file of the plurality of media files, wherein the one or more sets of object data comprises data about one or more objects displayed in the media file; forming, based on the associating, one or more media-object bindings between the one or more sets of object data and the at least the media file; storing the one or more media-object bindings in one or more databases; dynamically generating, based on the one or more sets of object data and the one or more media-object bindings, the play data associated with the media file; and displaying the play data in association the media file.
 24. The non-transitory computer-readable medium of claim 23, wherein the associating the one or more sets of object data with the media file to form the one or more media-object bindings further including associating a timestamp at which an associated object is displayed during in the at least the media file.
 25. The non-transitory computer-readable medium of claim 24, further comprising: sending the play data to be played simultaneously with the at least the media file based on the one or more media-object bindings.
 26. The non-transitory computer-readable medium of claim 25, wherein the sending further includes sending the timestamp so that the play data is displayed while the one or more objects are displayed during in the at least the media file.
 27. The non-transitory computer-readable medium of claim 23, further comprising: associating the one or more sets of object data with one or more named objects of a metadata reference container that maintains a common schema based on commonly experienced characteristics, the associating forming one or more object-object associations, wherein the play data is dynamically generated based on at least the one or more object-object associations.
 28. The non-transitory computer-readable medium of claim 27, wherein the metadata reference container maintains the common schema based on the commonly experienced characteristics for a plurality of different streaming media for different games provided by different media streaming servers.
 29. The non-transitory computer-readable medium of claim 27, wherein for different games, additional information are supplemented to the common schema by respective media streaming servers in order to provide in-depth and game-specific play data.
 30. The non-transitory computer-readable medium of claim 27, wherein the common schema is updated for new associations to form with the one or more sets of object data.
 31. The non-transitory computer-readable medium of claim 23, wherein the play data further includes an option to purchase regarding the one or more objects displayed in the media file.
 32. The non-transitory computer-readable medium of claim 23, wherein the play data further includes an option to purchase related information or gameplay options.
 33. The non-transitory computer-readable medium of claim 23, wherein the media file along with the play data are displayed as a live stream. 